Method and device for processing data during cell handover in lte system

ABSTRACT

A method and UE for processing data during cell handover in a Long Term Evolution (LTE) system are provided. The method includes: receiving, by User Equipment (UE), a Sequence Number (SN) of a Packet Data Convergence Protocol-Service Data Unit 
     (PDCP-SDU) that is received by a Source Evolved Node B (S_eNB) from a Target Evolved Node B (T_eNB); discarding, by the UE, the PDCP-SDU that is received by the S_eNB from a re-transmission queue, and re-transmitting other PDCP-SDUs in the queue to the T_eNB. Thereby, UE would not re-transmit PDCP-SDU corresponding to received SN, which avoids re-transmission of useless PDCP-SDU, and saves radio resources comparing with prior solutions.

The present application is a Continuation Application of U.S. patent application Ser. No. 12/677,502, filed on Mar. 10, 2010, which is a U.S. Nationalization of PCT Application Number PCT/CN08/72231, filed on Sep. 2, 2008, which claims priority to Chinese Patent Application No. 200710121647.X, entitled “METHOD FOR DATA RE-TRANSMISSION DURING CELL HANDOVER IN LTE SYSTEM AND APPARATUS THEREOF”, filed with Chinese Patent Office on Sep. 11, 2007, all of which are incorporated herein in their entireties.

FIELD

The present invention relates to the technical field of the Long Term Evolution (LTE) system in mobile communications, and particularly to a method for indicating data re-transmission during cell handover in the LTE system and a device thereof.

BACKGROUND

During the cell handover in the LTE system, the idea of User Equipment (UE) assistant to network control, i.e., the steps of “measure-report-decide-execute”, is still adopted. When the Source Evolved Node B (S_eNB) decides that the UE shall handover to the Target Evolved Node B (T_eNB) according to measurement reports from the UE and the T_eNB, the S_eNB exchanges information with the T_eNB directly via an X2 interface, to complete resource preparation in the target cell; then, the S_eNB instructs the UE to handover to the target cell; after a successful handover, the T_eNB informs the S_eNB to release radio resource of the original cell. In addition, the S_eNB transmits data that is not transmitted yet to the T_eNB and updates relation of nodes between a user plane and a control plane.

Referring to FIG. 1, a flowchart of cell handover in the LTE system in the prior art mainly includes:

[1] The S_eNB configures the UE with a measurement procedure;

[2] The UE sends a measurement report to the S_eNB;

[3] The S_eNB makes a UE handover decision according to the measurement report and Radio Resource Management (RRM) information;

[4] The S_eNB sends a handover request to the T_eNB;

[5] On receiving the handover request from the S_eNB, the T_eNB performs an admission control procedure according to the received E-RAB Quality of Service (QoS) information;

[6] The T_eNB sends a Handover Request Acknowledge message to the S_eNB;

[7] The S_eNB sends a Handover Command message to the UE, to instruct the UE to perform a handover;

[8] The UE sends a Synchronization message to the T_eNB;

[9] The T_eNB feeds a Synchronization Reply message back to the UE, the Synchronization Reply message including UL resource allocation information, a time advance, etc.;

[10] The UE sends a Handover Complete Acknowledge message to the T_eNB after the UE accesses the target cell successfully.

On the user plane, in order to avoid loss of uplink data from the UE and to maintain ordered transmission of the uplink data during the handover, an uplink data forwarding solution is adopted, which is performed between step [7] and step [8] of FIG. 1 (as illustrated by dotted lines). Generally, the data forwarding refers to that: the S_eNB forwards received disordered Packet Data Convergence Protocol-Service Data Units (PDCP-SDUs) to the T_eNB, and the PDCP-SDUs are attached with Sequence Numbers (SNs), then the T_eNB sends the received PDCP-SDUs to the Service Gateway (S-GW). During the handover, ordered transmission of upper layer PDUs is based on continuous PDCP-SNs and a re-order function provided by the PDCP layer. In the uplink, the re-order function of the PDCP layer of the T_eNB ensures the ordered transmission of the uplink PDCP-SDUs.

In the present LTE system, the air interface is based on the Automatic Repeat Request/Hybrid Automatic Repeat Request (ARQ/HARQ) mechanism. The S_eNB feeds ACKs back to the UE on successfully receiving ordered PDCP-SDUs. The UE re-transmits to the T_eNB those PDCP-SDUs whose ACKs are not received at the UE. It is not difficult to understand that the UE does not receive any ACK to a PDCP in two cases: in the first case, the S_eNB does not receive the PDCPs due to reasons such as network, etc., and does not feed ACKs back to the UE accordingly; in the second case, the S_eNB has received ordered PDCPs successfully, however, ACKs are not fed back to the UE successfully due to network reasons. The above second case may result in insignificant re-transmission from the UE to the T_eNB and a waste of precious radio resource. Examples are described hereinafter with reference to the two cases.

FIG. 2 illustrates a fact in which re-transmission of PDCP-SDUs from the UE results in an insignificant waste. The S_eNB receives data 1, 2 and 3 from the UE successfully and transmits the data 1, 2 and 3 to the S-GW via an S1 interface. It is assumed that the UE receives only an ACK to the data 1 fed back from the network side and does not receive ACKs to the data 2 and 3. In this case, the UE continues to send the data 2 and 3 to the T_eNB, the T_eNB receives the data 2 and 3 and sends the re-transmitted data 2 and 3 to the S-GW, which results in reception of repeated data in the Evolved Packet Core (EPC) system and a waste of precious radio resource at the air interface.

FIG. 3 illustrates another fact in which re-transmission of PDCP-SDUs from the UE results in an insignificant waste. The UE sends data a, b, c and d to the S_eNB, however, the data b fails during transmission and the S_eNB receives only the data a, c and d, and the data c and d becomes disordered. According to the conventional solution of data forwarding, the S_eNB sends the ordered data a to the S-GW, buffers the disordered data c and d in a buffer, and then sends the data c and d to the T_eNB which delivers the data c and d to the S-GW. It is assumed that the UE does not receive any ACK to the data c and d. In this case, the UE receives only an ACK to the data a, and re-transmits the data b, c and d to the T_eNB because the UE does not receive any ACK to the data b, c and d. Apparently, the data c and d is re-transmitted. On one hand, the S_eNB sends the buffered data c and d to the T_eNB; on the other hand, the UE re-transmits the data c and d to the T_eNB due to no reception of any ACK, thereby resulting in a waste of resource.

SUMMARY

In view of this, the present invention provides a method for processing data during cell handover in a Long Term Evolution (LTE) system, so as to solve the problem of waste of radio resource due to re-transmission of redundant PDCP-SDUs in the conventional solution.

Corresponding to the method, the present invention further provides a device for processing data during cell handover in a Long Term Evolution (LTE) system, i.e., a UE.

The technical solution of the present invention is described as follows.

A method for processing data during cell handover in a Long Term Evolution (LTE) system includes:

-   -   receiving, by User Equipment (UE), a Sequence Number (SN) of a         Packet Data Convergence Protocol-Service Data Unit (PDCP-SDU)         that is received by a Source Evolved Node B (S_eNB) from a         Target Evolved Node B (T_eNB);     -   discarding, by the UE, the PDCP-SDU that is received by the         S_eNB from a re-transmission queue, and re-transmitting other         PDCP-SDUs in the queue to the T_eNB.

The UE receives the SN of the PDCP-SDU that is received by the S_eNB through a synchronization reply message, a Radio Resource Control (RRC) message, a Radio Link Control (RLC) message or a Media Access Control (MAC) message.

The method further includes:

-   -   receiving, by the UE, a Handover Command message from the S_eNB;         and     -   performing, by the UE, handover based on the Handover Command         message.

A User Equipment (UE) for processing data during cell handover in a Long Term Evolution (LTE) system includes: an Evolved Node B (eNB) interface unit and a queue adjustment unit, where

-   -   the eNB interface unit is adapted to receive a Sequence Number         (SN) of a Packet Data Convergence Protocol-Service Data Unit         (PDCP-SDU) that is received by a Source Evolved Node B (S_eNB)         from a Target Evolved Node B (T_eNB);     -   the queue adjustment unit is configured to discard the PDCP-SDU         that is received by the S_eNB from a re-transmission queue;     -   the eNB interface unit is further configured to re-transmit         other PDCP-SDUs in the queue to the T_eNB.

The UE further includes: a re-transmission queue and a message parsing unit, where

-   -   the re-transmission queue is adapted to buffer PDCP-SDUs; and     -   the message parsing unit is adapted to parse a message to obtain         the SN of the PDCP-SDU that is received by the S_eNB.

The above technical solution includes the following technical effects.

In the solution of cell handover in the LTE system according to the prior art, the UE re-transmits a PDCP to the T_eNB if only the UE does not receive an ACK to the PDCP. However, in the present invention, the UE further determines whether the UE has received from the T_eNB a PDCP-SN indicating that the S_eNB has received the PDCP. If the UE does not receive the ACK to the PDCP but receives the PDCP-SN indicating that the S_eNB has received the PDCP, the UE does not re-transmit the PDCP, thereby avoiding re-transmission of redundant PDCPs and resulting in effective saving of radio resource compared with the conventional solution.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of cell handover in the LTE system in the prior art;

FIG. 2 is a first diagram of resending data from the UE in the prior art;

FIG. 3 is a second diagram of resending data from the UE in the prior art;

FIG. 4 is a diagram of a first embodiment of the method according to the present invention;

FIG. 5 is a flowchart of the first embodiment of the method according to the present invention;

FIG. 6 is an exemplary diagram of the first embodiment of the method according to the present invention;

FIG. 7 is a flowchart of a second embodiment of the method according to the present invention;

FIG. 8 is a flowchart of a third embodiment of the method according to the present invention;

FIG. 9 is a diagram of a structure of an S_eNB device according to the present invention;

FIG. 10 is a diagram of a structure of a T_eNB device according to the present invention; and

FIG. 11 is a diagram of a structure of a UE device according to the present invention.

DETAILED DESCRIPTION

The core of the present invention lies in that a process is added during cell handover of the UE, i.e., the S_eNB informs the UE via the T_eNB that which PDCP-SDUs have been received by the S_eNB successfully and the UE does not need to re-transmit the PDCP-SDUs even if the UE does not receive ACKs to the PDCP-SDUs.

Further, the present invention is implemented in the following manner:

-   -   1] The S_eNB sends a PDCP-SDU SN report to the T_eNB, to inform         the T_eNB of PDCP-SDU SNs (including SNs of all ordered and         unordered PDCP-SDUs) that have been received by the S_eNB;     -   2] The T_eNB re-transmits the PDCP-SDU SNs to the UE according         to the report, to inform the UE which PDCP-SDUs have been         received;     -   3] The UE does not re-transmit the PDCP-SDUs according to the         received PDCP-SDU SNs.

In the solution of cell handover in the LTE system in the prior art, the UE re-transmits a PDCP-SDU to the T_eNB if only the UE does not receive an ACK to the PDCP-SDU. However, in the present invention, the UE further determines whether the UE has received from the T_eNB the SN indicating that the S_eNB has received the PDCP-SDU. If the UE does not receive an ACK to a PDCP-SDU but receives a PDCP-SDU SN indicating reception of the PDCP-SDU, the UE does not re-transmit the PDCP-SDU, thereby avoiding re-transmission of duplicate PDCP-SDU and resulting in effective saving of radio resource compared with the conventional solution.

Embodiments of the present invention are described in detail hereinafter with reference to the accompanying drawings.

It is not difficult to understand that a signaling is added in cell handover according to the present invention, so as to transmit the PDCP-SDU SNs that have been received by the S_eNB. The UE does not re-transmit the PDCP-SDUs. In order to make the whole procedure more clear, the procedure of cell handover in the LTE system, i.e., a modified solution based on the cell handover described in the background of the invention, is described hereinafter.

FIG. 4 is a diagram of cell handover in the LTE system according to the first embodiment. The cell handover includes the following steps.

In step 401, the S_eNB configures the UE with a measurement procedure according to roaming restriction information.

The measurement information provided by the S_eNB may be of assistance to control the connection mobility function of the UE.

In step 402, the UE sends a measurement report to the S_eNB.

In step 403, the S_eNB makes a handover decision to perform cell handover of the UE according to the measurement report from the UE and RRM information.

In step 404, the S_eNB sends to the T_eNB a Handover Request message carrying necessary information so that the T_eNB prepares handover resource. The Handover Request message also indicates whether the system supports DL/UL data forwarding, and the Handover Request message further includes a SAE bearer context.

The SAE bearer context includes Transport Network Layer (TNL) information of the S-GW for transmitting upper layer data, QoS information born by SAE, etc.

In step 405, the T_eNB performs an admission control procedure based on the received QoS information born by SAE.

In step 406, the T_eNB sends a Handover Request Acknowledge message to the S_eNB while preparing the handover resource.

The Handover Request Acknowledge message includes a Tunnel End Point Identifier (TEID) and an address of TNL supporting DL/UL data forwarding allocated by the T_eNB.

In step 407, the S_eNB sends a Handover Command message to the UE to instruct the UE to perform handover on receiving the Handover Request Acknowledge message from the T_eNB.

The Handover Command message includes a new Radio Network Temporary Identity (RNTI), a possible starting time, a System Information Block (SIB) of the T_eNB, etc.

On receiving the Handover Command message from the S_eNB, the UE ceases sending PDCP-SDUs to the S_eNB. The UE may utilize a Radio Link Control (RLC) Acknowledge procedure or other mechanisms to ensure proper reception of the Handover Command message.

After sending the Handover Command message, the S_eNB commences performing the UL/DL data forwarding, i.e., buffers the PDCP-SDUs received from the UE in the Buffer and sends the PDCP-SDUs to the T_eNB.

In step 408, the S_eNB sends a “PDCP-SN report” to the T_eNB via an X2 interface to inform the T_eNB of SNs of all received PDCP-SDUs on receiving the RLC layer Acknowledge message in response to the Handover Command message or after the S_eNB waits for a period of time in case of receiving no RLC layer Acknowledge message.

The above-mentioned period of time in case of receiving no RLC layer Acknowledge message depends on the possible starting time of the Handover Command message.

In step 409, the UE sends a Synchronization message to the T_eNB to request synchronization with the T_eNB once the possible starting time of the Handover Command message arrives. Then, the T_eNB begins to obtain the time advance of the UE.

In step 410, after the UE is synchronized with the T_eNB, the T_eNB sends to the UE a Synchronization Reply message including UL resource allocation information, the time advance, the PDCP-SNs of the PDCP-SN report, etc.

The T_eNB may possibly not receive the PDCP-SN report from the S_eNB in time due to the delay of the X2 interface after the UE is synchronized with the T_eNB. If the T_eNB has not received the PDCP-SN report when replying to the UE, the Synchronization Reply message does not include the PDCP-SNs; otherwise the Synchronization Reply message includes the PDCP-SNs.

The UE discards corresponding PDCPs from the re-transmission queue according to the indication of PDCP-SNs for the purpose of saving rare resource of the air interface. The UE proceeds as the prior art in case of no PDCP-SNs. It can be seen that the solution according to the present invention is easy to be compatible with the prior art.

In step 411, the UE sends a Handover Confirm message to the T_eNB after the UE accesses the target cell successfully, to inform of the completion of handover procedure.

Therefore, the present invention emphasizes on addition of step 408, modification to step 410, and subsequent re-transmission of PDCPs at the UE.

FIG. 5 is a flowchart of the first embodiment, which includes step 501 to step 506.

In step 501, after the S_eNB sends the Handover Command message to the UE, the S_eNB sends a PDCP-SN report to the T_eNB on receiving an RLC Acknowledge message or after the S_eNB waits for a period of time.

In step 502, it is determined whether the T_eNB has received the PDCP-SN report from the S_eNB after the UE synchronizes with the T_eNB. The branch of step 503 is executed if the T_eNB has received the PDCP-SN report from the S_eNB. The branch of step 505 is executed if the T_eNB has not received the PDCP-SN report from the S_eNB.

In step 503, the T_eNB sends a Synchronization Reply message carrying PDCP-SNs to the UE.

In step 504, the UE discards PDCP SDUs corresponding to the PDCP-SNs from a PDCP re-transmission queue in which corresponding ACKs are not received, and re-transmits only the rest of PDCP-SDUs in the re-transmission queue to the T_eNB.

In step 505, the T_eNB sends a Synchronization Reply message to the UE. Being the same as that in the conventional solution, the Synchronization Reply message includes UL resource allocation information and a time advance.

In step 506, the UE re-transmits to the T_eNB all PDCP-SDUs whose ACKs are not received.

With the present invention, insignificant re-transmission of PDCP-SDUs from the UE to the T_eNB can be avoided.

Also taking the scenario as illustrated in FIG. 3 as an example, the UE sends data a, b, c and d to the S_eNB, however, the data b fails during transmission, and the UE does not receive any ACK to the data b according. The S_eNB receives only the data a, c and d, and the data c and d becomes disordered. It is assumed that the UE does not receive any ACK to the data c and d. According to the solution of this embodiment, the S_eNB adds a step of assembling the PDCP-SDU SN report for the received PDCP-SDUs based on the conventional procedure. The PDCP-SDU SN report includes SNs of the data a, c and d. The S_eNB delivers the PDCP-SDU SN report to the T_eNB at an appropriate time (on receiving the RLC Acknowledge message, or after the S_eNB waits for a period of time). The T_eNB informs the UE that which PDCP-SDUs have been received by the S_eNB successfully through a Synchronization Reply message, i.e., the data a, c and d has been received, which need not to be re-transmitted. The UE receives only an ACK to the data a, and puts the data b, c and d to the re-transmission queue for re-transmission. However, the UE discards the data c and d from the re-transmission queue because the UE knows from the Synchronization Reply message that the data c and d has been received by the S_eNB. That is, the UE re-transmits only the failed data b to the T_eNB. Compared with the conventional solution, re-transmission of the data c and d (the S_eNB forwards the data c and d to the T_eNB by data forwarding) can be avoided, saving precious radio resource of the air interface. A diagram of processing the scenario of FIG. 3 by using this embodiment is illustrated in FIG. 6.

The second embodiment of the method according to the present invention is described hereinafter.

In the above first embodiment, the T_eNB sends a Reply message including no PDCP-SDU SN to the UE in a conventional manner after the synchronization of the UE in case of receiving no PDCP-SDU SN. In contrast, the T_eNB sends a Reply message to the UE after receiving PDCP-SDU SNs within a preset period of time in the second embodiment, delivering the PDCP-SDU SNs to the UE as far as possible and ensuring no re-transmission of redundant PDCP-SDUs from the UE.

FIG. 7 is a flowchart of the second embodiment, which includes step 701 to step 707.

In step 701, after the S_eNB sends a Handover Command message to the UE, the S_eNB sends a PDCP-SDU SN report to the T_eNB on receiving an RLC Acknowledge message or after the S_eNB waits for a period of time.

In step 702, it is determined whether the T_eNB has received the PDCP-SDU SN report from the S_eNB after the UE is synchronized with the T_eNB. The branch of step 703 is executed if the T_eNB has received the PDCP- SDU SN report from the S_eNB. The branch of step 705 is executed if the T_eNB has not received the PDCP- SDU SN report from the S_eNB.

In step 703, the T_eNB sends a Synchronization Reply message carrying PDCP-SDU SNs to the UE.

In step 704, the UE discards PDCP-SDUs corresponding to the PDCP-SDU SNs from the PDCP re-transmission queue in which corresponding ACKs are not received, and re-transmits only the rest of PDCP-SDUs in the re-transmission queue to the T_eNB.

In step 705, it is determined whether the PDCP-SN report is received within a preset period of time. Step 703 is executed if the PDCP-SN report is received within a preset period of time. Step 706 is executed if the waiting time exceeds the period of time.

There is a plurality of reasons for failing to receive the PDCP-SN report, such as the delay of the X2 interface, or the network transmission congestion, or improper parsing of the received PDCP-SDU SNs at the T_eNB, in this case, step 706 is executed.

In step 706, the T_eNB sends a Synchronization Reply message to the UE. As being the same as that in the conventional solution, the Synchronization Reply message includes only UL resource allocation information and a time advance.

In step 707, the UE re-transmits all PDCP-SDUs whose ACKs are not received to the T_eNB.

Based on the first embodiment, the T_eNB does not send the Synchronization Reply message immediately in case of not receiving the PDCP-SDU SN report but waits for a period of time according to the second embodiment, further ensuring the reception of the Synchronization Reply message including PDCP-SDU SNs and further effectively ensuring saving of radio resource.

The third embodiment of the present invention is described hereinafter.

The third embodiment differs from the above two embodiments in that the processing of T_eNB after step 408. In the third embodiment, the T_eNB carries the PDCP-SDU SNs in the Reply message to the UE if the T_eNB has received the PDCP-SDU SN report from the S_eNB before the synchronization of UE. The T_eNB does not carry the PDCP-SDU SNs in the Reply message to the UE if the T_eNB has not received the PDCP-SDU SN report from the S_eNB after the synchronization of UE, but sends an RRC message, an RLC message or a MAC message to the UE carrying the PDCP-SDU SNs immediately once the T_eNB receives the PDCP-SDU SN report. Accordingly, the UE discards PDCP-SDUs corresponding to the PDCP-SDU SNs carried in the RRC message, the RLC message or the MAC message from the re-transmission queue, and re-transmits the rest of PDCP-SDUs of the queue to the T_eNB.

FIG. 8 is flowchart of the third embodiment, which includes step 801 to step 808.

In step 801, after the S_eNB sends a Handover Command message to the UE, the S_eNB sends a PDCP-SDU SN report to the T_eNB on receiving an RLC Acknowledge message or after the S_eNB waits for a period of time.

In step 802, it is determined whether the T_eNB has received the PDCP-SDU SN report sent from the S_eNB after the UE is synchronized with the T_eNB. The branch of step 803 is executed if the T_eNB has received the PDCP-SDU SN report sent from the S_eNB, otherwise the branch of step 805 is executed.

In step 803, the T_eNB sends to the UE a Synchronization Reply message carrying PDCP-SDU SNs.

In step 804, the UE discards PDCP-SDUs corresponding to the PDCP-SDU SNs from the PDCP-SDU re-transmission queue in which corresponding ACKs are not received, and re-transmits only the rest of PDCP-SDUs in the re-transmission queue to the T_eNB.

In step 805, the T_eNB sends a Synchronization Reply message to the UE. As being the same as that in the conventional solution, the Synchronization Reply message includes only UL resource allocation information and a time advance.

In step 806, the T_eNB receives the PDCP-SDU SN report sent from the S_eNB.

In step 807, the T_eNB sends to the UE an RRC message, an RLC message or a MAC message carrying the PDCP-SDU SNs immediately.

In step 808, the UE discards PDCP-SDUs corresponding to the PDCP-SDU SNs carried in the RRC message, the RLC message or the MAC message from the re-transmission queue, and re-transmits only the rest of PDCP-SDUs in the queue to the T_eNB.

In this embodiment, the T_eNB still sends the Synchronization Reply message to the UE in the prior art in case of receiving no PDCP-SN report, which is well compatible with the prior art. The T_eNB sends to the UE the RRC message, the RLC message or the MAC message immediately so that the possibility of re-transmitting redundant PDCP-SDUs is reduced to the least extent, ensuring effective and reasonable utilization of radio resource.

A diagram of a structure of an S_eNB according to the present invention is illustrated in FIG. 9. Besides an X2 interface unit 901 communicated with the T_eNB and a UE interface unit 902 communicated with the UE, the S_eNB includes a report assembling unit 903.

The report assembling unit 903 is mainly responsible for assembling a PDCP-SDU SN report including SNs of PDCP-SDUs received at the UE interface unit 902. The PDCP-SDU SN report is sent to the T_eNB at an appropriate time (on receiving an RLC Acknowledge message, or after the report assembling unit 903 waits for a period of time) via the X2 interface unit 901.

A diagram of a structure of a T_eNB according to the present invention is illustrated in FIG. 10. Besides an X2 interface unit 1001 communicated with the S_eNB and a UE interface unit 1002 communicated with the UE, the T_eNB includes a message assembling unit 1003.

The message assembling unit 1003 is mainly responsible for assembling a message including the PDCP-SDU SNs received at the S_eNB. Based on the functions of respective units of the conventional T_eNB, the X2 interface unit 1001 is further adapted to receive the PDCP-SDU SN report sent from the S_eNB, the report including the PDCP-SDU SNs received at the S_eNB. The UE interface unit 1002 is further adapted to send the message assembled by the message assembling unit 1003 to the UE. The message assembled by the message assembling unit 1003 may be a Synchronization Reply message, an RRC message, an RLC message, or a MAC message.

A diagram of a structure of a UE according to the present invention is illustrated in FIG. 11. Besides an eNB interface unit 1101 communicated with the S_eNB or the T_eNB and a re-transmission queue 1102 in which PDCP-SDUs are buffered, the UE includes a message parsing unit 1103 and a queue adjustment unit 1104.

Based on conventional functions, the eNB interface unit 1101 is further adapted to receive from the T_eNB a message indicating PDCP-SDU SNs that have been received by the S_eNB. The message parsing unit 1103 is mainly responsible for parsing the message to obtain the PDCP-SDU SNs that have been received by the S_eNB. The queue adjustment unit 1104 is mainly responsible for discarding the PDCP-SDU SNs that have been received by the S_eNB from the re-transmission queue 1102. Accordingly, the eNB interface unit 1101 re-transmits the rest of PDCP-SDUs in the re-transmission queue 1102 to the T_eNB. The message indicating the PDCP-SDU SNs that have been received by the S_eNB may be a Synchronization Reply message, an RRC message, an RLC message, or a MAC message.

Reference can be made to the aforementioned method embodiments for specific implementations of the S_eNB, the T_eNB and the UE according to the present invention, which is not repeated here.

The above description is merely for preferred embodiments of the present invention.

It should be noted that an ordinary skill in the art without departing from the scope of the present invention can make a plurality of changes and modifications, which shall be encompassed in the protection scope of the present invention. 

1. A method for processing data during cell handover in a Long Term Evolution (LTE) system, comprising: receiving, by User Equipment (UE), a Sequence Number (SN) of a Packet Data Convergence Protocol-Service Data Unit (PDCP-SDU) that is received by a Source Evolved Node B (S_eNB) from a Target Evolved Node B (T_eNB); discarding, by the UE, the PDCP-SDU that is received by the S_eNB from a re-transmission queue, and re-transmitting other PDCP-SDUs in the queue to the T_eNB.
 2. The method according to claim 1, wherein the UE receives the SN of the PDCP-SDU that is received by the S_eNB through a synchronization reply message, a Radio Resource Control (RRC) message, a Radio Link Control (RLC) message or a Media Access Control (MAC) message.
 3. The method according to claim 2, further comprising: receiving, by the UE, a Handover Command message from the S_eNB; and performing, by the UE, handover based on the Handover Command message.
 4. A User Equipment (UE) for processing data during cell handover in a Long Term Evolution (LTE) system, comprising: an Evolved Node B (eNB) interface unit and a queue adjustment unit, wherein the eNB interface unit is adapted to receive a Sequence Number (SN) of a Packet Data Convergence Protocol-Service Data Unit (PDCP-SDU) that is received by a Source Evolved Node B (S_eNB) from a Target Evolved Node B (T_eNB); the queue adjustment unit is configured to discard the PDCP-SDU that is received by the S_eNB from a re-transmission queue; the eNB interface unit is further configured to re-transmit other PDCP-SDUs in the queue to the T_eNB.
 5. The UE according to claim 4, further comprising: a re-transmission queue and a message parsing unit, wherein the re-transmission queue is adapted to buffer PDCP-SDUs; and the message parsing unit is adapted to parse a message to obtain the SN of the PDCP-SDU that is received by the S_eNB. 